Fix several memory leaks

Addressed issues:

• Undestroyed Angular animations
• Wrong addEventListeners using .bind() in-place.
• .destroy() dynamic components created with createComponent()
• .destroy() dynamic components created using ViewContainerRef.createComponent() but then detached from it.

Leak detection

Add leaks detection to the configureTestSuite().
If chrome is started with --js-flags="--expose-gc" it will track all created fixtures and perform a gc() at the end of the suite and it will report any leaked instances in memory.
Also, it's performing the moduleRef.destroy() for all created modules that was missing before.

The leak detection is opt-in for every suite because there are many existing issues and it may also report false positives for example:

• When some timeout / requestAnimationFrame is pending to execute at the end of the test
• When the reference is created beforeEach() but it's not cleaned up afterEach()

Not all leaks will be detected. For example a component retained by a root service, in the lifecycle of the test it will be disposed but in a real app lifecycle this should be considered a leak.

Additional information (check all that apply):

• Bug fix
• New functionality
• Documentation
• Demos
• CI/CD

Checklist:

• All relevant tags have been applied to this PR
• This PR includes unit tests covering all the new code (test guidelines)
• This PR includes API docs for newly added methods/properties (api docs guidelines)
• This PR includes feature/README.MD updates for the feature docs
• This PR includes general feature table updates in the root README.MD
• This PR includes CHANGELOG.MD updates for newly added functionality
• This PR contains breaking changes
• This PR includes ng update migrations for the breaking changes (migrations guidelines)
• This PR includes behavioral changes and the feature specification has been updated with them